Business rules manager

ABSTRACT

An apparatus and method is provided for creating, updating, and deleting business rules with ease by use of a rule manager. Business rules are represented as tables that map a set of inputs to a set of outputs. Inputs are represented as enumerations with predefined allowable values. All possible unique combinations of values for a given set of inputs are automatically generated, and a business user can then set the outputs for each desired input value combination.

CROSS REFERENCE TO RELATED APPLICATIONS

This application is a continuation of U.S. patent application Ser. No.13/908,961, entitled “BUSINESS RULES MANAGER”, filed on Jun. 3, 2013,which claims priority to U.S. Provisional Patent Application Aerial No.61/657,178, entitled “BUSINESS RULES MANAGER”, filed Jun. 8, 2012, eachof which are incorporated herein in their entirety by this referencethereto.

BACKGROUND OF THE INVENTION

1. Technical Field

The invention relates to automated business systems. More particularly,the invention relates to a user friendly business rules managementsystem.

2. Description of the Background Art

A business rules engine is a software system that executes one or morebusiness rules in a runtime production environment. Business ruleengines typically support rules, facts, priority (score), mutualexclusion, preconditions, and other functions. Business rule enginesoftware is commonly provided as a component of a business rulemanagement system which, among other functions, provides the ability tocreate, read, modify, and delete the rules, verify consistency of rulesdefinitions, and define the relationships between different rules.

Most existing business rule frameworks rely on sets of conditionalexpressions that require Boolean operators, such as AND, OR, and NOT,which are difficult for business users to write and understand,especially when there are more than a few expressions.

Further, in existing systems, when multiple rules are used, they must beordered. A common approach is to evaluate the rules in order, with laterrules overriding earlier ones. A new rule cannot be simply added to thestart or the end of the list. Instead, it must be added so that itsorder is after the rules that it should override, but before the rulesthat it should be overridden by.

Furthermore, a system or user who wants to compute a desired outputvariable cannot simply scan the rules from the start until one is foundwhose conditions match the current state of the inputs. Instead, all thelater rules must also be considered in case one overrides a precedingrule. As a result, the process of creating and evaluating rules is timeconsuming and confusing.

Therefore, present systems make the tasks of making and updatingbusiness rules difficult and time consuming. This complexity oftenprevents non-technical users from understanding and managing thebusiness rules in their organization.

SUMMARY OF THE INVENTION

Embodiments of the invention provide an apparatus and method forcreating, updating, and deleting business rules with ease by use of arule manager. The invention represents business rules as tables that mapa set of inputs to a set of outputs. Furthermore, inputs are representedas enumerations with predefined allowable values. Thus, an embodiment ofthe invention automatically generates all possible unique combinationsof values for a given set of inputs, and allows a business user to setthe outputs for each desired input value combination.

BRIEF DESCRIPTION OF THE DRAWINGS

FIG. 1 is a block schematic diagram showing a general system in anautomated business environment according to the invention;

FIG. 2A is a block schematic diagram showing the manner in which Inputdata is arranged in the form of Attributes and Enumerators according tothe invention;

FIG. 2B shows a rules table that maps a set of inputs to a set ofoutputs, resulting in a single output combination for a selectedcombination of inputs according to the invention;

FIG. 3 shows a table that illustrates an embodiment of the inventionwhich includes a wild card feature;

FIG. 4 is a flowchart that shows, for a rules manager, the logical stepsa business user goes through to define and update business rulesaccording to the invention; and

FIG. 5 is a block schematic diagram that depicts a machine in theexemplary form of a computer system within which a set of instructionsfor causing the machine to perform any of the herein disclosedmethodologies may be executed.

DETAILED DESCRIPTION OF THE INVENTION

Embodiments of the invention provide an apparatus and method forcreating, updating, and deleting business rules with ease by use of arule manager. Thus, an embodiment of the invention automaticallygenerates all possible unique combinations of values for a given set ofinputs, referred to as attributes, and allows a business user to set theoutput values for each desired input combination. A presently preferredembodiment of the invention provides an administrative environment forcreating, maintaining and managing business rules, and a runtimeinterface with which applications can evaluate the rules in real-time.This makes a business rules system in accordance with the invention morereadable, updateable, and understandable and enhances the experience ofthe business user and any other person interested.

Embodiments of the invention provide a general purpose rules manager.The invention allows data to be externally documented, rather thanburied in the system code, thus enabling the business user to create,read, modify, and delete rules with ease by himself, without involvingtechnical assistance. The invention also allows a business user toperform updates of the business rules in real time. The inventionprovides a system that is understandable to business users, thus makingit more usable.

In an embodiment of the invention, a rules manager uses tables to mapattributes, i.e. the inputs or independent variables, to settings, i.e.the outputs or dependent variables. Attributes are used to represent theknown state of an application session in which rules are evaluated. Forexample, attributes could be used to capture the profile, transactions,and behavior of a particular user. A setting is a parameter of interestto the application. In the case of an application that recommends a newmobile phone to a customer, the attributes could be the customer'slocation, current mobile phone, and wireless plan, and the settingscould be the recommended phone, recommended plan, available accessories,and a special promotional offer.

In an embodiment, each attribute is an enumeration, which means that ithas a set of allowable values referred to as enumerators. If anattribute represents an entity with discrete values, e.g. locations,phone types, phone numbers, enumerators may represent one more discretevalues through association, classification, grouping or any othertechnique that assigns every discrete value to at most one enumerator.If an attribute represents an entity with numerical values, e.g. prices,temperatures, etc., enumerators may represent one or more ranges ofvalues such that every numerical value may belong to at most oneenumerator.

A tuple represents a possible combination of enumerators for one or moreattributes. When a set of attributes is declared, a rules manager canautomatically generate the tuples that represent all the possiblecombination of enumerators. A business user can then define the outcomeassociated with a tuple by specifying the value of settings thatcorrespond to each tuple. The outcome of a tuple is independent from theoutcome of any other tuple, i.e. the outcome of one tuple cannotoverride the outcome of another tuple. A user who wants to understandthe outcome for a particular combination of enumerators therefore onlyneeds to find the tuple that represents that combination of enumerators.

Embodiments of the invention also allow the use of a wild card entry asan attribute value in a tuple to indicate all possible enumerators forthat attribute. An operation is provided to expand a tuple with a wildcard entry to a set of tuples, each of which contains a singleenumerator of the expanded attribute. A reverse operation is alsoavailable that collapses a set of all tuples that are identical, exceptfor the value of a given attribute, into a single tuple that has a wildcard entry for that attribute.

FIG. 1 is a block schematic diagram showing an automated businessenvironment according to the invention. The invention as depictedcomprises a business user 101, a business rules manager 102, and abusiness application 103. The application can be any general purposesystem supported by a backend data base. The application calls upon abusiness rules manager, as described in detail in the description tofollow. The business user can access the administrative environment ofthe business rules manager to create, read, modify, and delete businessrules. The application sets attributes to values that represent theknown state of a particular session, and uses the business rules managerto return the values of desired settings for that particular session.

FIG. 2A illustrates the manner in which input data 201 is arranged inthe form of attributes 203 and enumerators 202, and FIG. 2B shows arules table 204 that maps each combination of enumerators of theattributes 205 to the values of one or more settings, i.e. the outputs206, according to the invention. The embodiment of the invention shownin FIGS. 2A and 2B uses an illustrative example to describe the rulestable in detail, but it should not be considered as a limitingapplication. The example in FIGS. 2A and 2B concerns an upgrade policyand the features that a service provider offers to its customers, basedon the customer's market and phone type.

FIG. 2A shows a set of attributes 201, in which each attribute 203 has aset of enumerators, i.e. possible values 202.

FIG. 2B shows a rules table 204 maintained by the business rules managercomprising of set of tuples 205 and settings 206. An attribute 203 is aninput variable, such as market, type of phone, etc. Each attribute has aset of allowed values referred to as enumerators 202. For example, theMarket attribute has enumerators, such as the names of the markets, e.g.Boston, Atlanta, etc., while the Phone Type attribute has enumerators,such as the types of phones, e.g. iPhone, Android, Blackberry, etc.

The attributes and enumerators can be accessed, updated, or newlycreated by the business user. The rule runtime system ensures that ateach point in time, every attribute is set to an allowable value. Thiscan be achieved by declaring a default enumerator for the attribute thatis used to initialize the attribute's value at the start of eachsession. Moreover, any attempt to set the attribute to a value that isnot among the set of enumerators is rejected. In such cases, theattribute can retain its previous value or can be reset to the defaultenumerator according to different embodiments of the invention.

The rules table contains a set of tuples, where each tuple representsone or more attribute value combinations. The rules table pre-fills theset of tuples that represents all of the possible combinations ofenumerators by generating the Cartesian product of all attributes. Someof the pre-filled tuples can be removed by the business user if thecombinations of enumerators they represent are not necessary.

The system allows the value of a setting (output) to be specified foreach tuple by the business user. As shown in the rules table 204,Atlanta—Blackberry, Atlanta—iPhone, Boston—Blackberry, Boston—iPhone arethe possible set of tuples pre-filled by the system whileYes—Chat—Ringtones, Yes—Ringtones, No-Ringtones are settings 206inputted by the business user.

The system uses a data structure that holds only one instance of eachtuple, thus ensuring that each possible attribute value combination isrepresented by one and only one tuple. As shown, for the tuple thatrepresents the Atlanta market and phone type iPhone there is one andonly one row of settings (output) 206 specifying whether upgrades aresupported and the additional features allowed. As for the example inthis embodiment, upgrades are supported, and the additional featuresallowed are: Chat, ring tones, and video streaming.

Another embodiment of the invention allows addition, deletion, ormodification of the enumerators for an attribute. The systemrecalculates the set of tuples upon each enumerator change to ensurethat all possible valid attribute value combinations are present, andthat no invalid attribute value combinations, i.e. those that containattribute values that are not in the attribute's set of enumerators, arepresent. When an enumerator is added to an attribute, the systemautomatically updates all tables that contain that attribute to add thetuples that contain the new enumerator. The setting values for thepreviously existing tuples are left unchanged. When an enumerator isremoved from an attribute, the system automatically updates all tablesthat contain that attribute by deleting all tuples that include theremoved enumerator.

A rules table maps one or more attributes to one or more settings. Whentwo settings are in one rules table, the two settings must both dependon the same set of attributes. Separate rules tables can be created tosupport different sets of attributes and the settings that depend onthose attributes.

The state of a particular session is represented by the values of theattributes. A tuple represents an attribute value combination. Each rowof the rules table contains a unique tuple. As a result, the state ofthe session corresponds to a specific row and the order of the rows isirrelevant. To find a combination of attribute values, rows can besorted or filtered in any way. Thus, a business user can specify anoutput variable (setting) for a tuple without worrying about the othertuples.

Another advantage of the invention is that the business application hasknowledge of the attributes and settings, but not of the contents of therules tables themselves, i.e. the application does not need to know theset of attributes that affect a setting. The business application isresponsible for setting the values of the attributes to represent thestate of the current session and can ask the business rules manager todetermine the values of one or more settings. In one embodiment of theinvention, each setting is present in only one rules table. Thus, theapplication does not need to specify the rules table to use; instead,the system looks up the single rules table that contains the desiredsetting. Therefore, the rules tables can be updated and restructured,e.g. attributes can be added or removed and settings can be moved fromone table to another, without touching the business application. Theapplication automatically picks up the latest business rules without anyrecompilation or redeployment.

FIG. 3 illustrates another embodiment of the invention by providing anillustrative example that explains the wild card feature. A wildcardrepresents all enumerators for an attribute. This example shows a rulestable having attributes (inputs), such as plan, phone type, and marketthat a service provider can offer, while the settings (outputs) displaypromotional offers for the input combinations. In the example of FIG. 3,the tuple with Plan 140 and Phone Type Blackberry has a wildcard in theMarket attribute column, which indicates that the tuple represents allpossible enumerators of the Market attribute, i.e. all Markets.

Attribute order is significant when using a wildcard. If a tuple has awildcard in one attribute, then all the following attributes are alsoset to wild cards. This requirement ensures that each possible attributevalue combination is represented by one and only one tuple, This can beseen in the row corresponding to Plan I50, where a wildcard entry in the‘Phone type’ column automatically sets the following attribute (Market)with a wildcard.

A tuple can represent many attribute value combinations through the useof wildcards. Collapsing tuples replaces a set of related tuples with asingle tuple that contains wildcards. Expanding a tuple that has awildcard replaces it with many tuples by expanding the wildcard into allof its possible value combinations.

In one embodiment, the invention allows the rules to be eithersystem-managed, i.e. allowing the system to generate rules for allcombinations of all input values, or client-managed (business user),i.e. allowing a client to define rules for a subset of the attributevalue combinations.

The invention provides an ability to work within an administrationframework that allows role-based access control to various ruleoperations. Embodiments of the invention support multiple versions ofthe rule base, thus allowing multiple rule bases to be in useconcurrently during different parts of a business application's lifecycle. For example, different versions of the rule base may be used fordevelopment and production versions of the application, thus allowingrules to be tested and verified in the development environment beforebeing promoted to the production environment.

In one embodiment, the invention supports snapshots that capture thestate of the rule base at a point in time, for later reinstatement. Thesystem provides both automatic snapshots and user-determined snapshotsfor backup and recovery in cases where changes have been made to therule base that need to be rolled back.

FIG. 4 is flow diagram showing operation of the rules manager module viathe logical steps that a business user can go through to define andupdate business rules according to the invention. As shown in in FIG. 4,the business user opens the business rules manager administrativeenvironment (201) and tries to perform actions, such as adding a newrules table, updating existing rules tables, etc. The business rulesmanager checks if the business user wants to add or update an attribute(202). If so, the business user creates or updates an attribute and itsset of enumerators (203). The business user then defines one or morerules tables, each of which contains a specified set of attributes(204). The business rules manager then generates tuples to representpossible attribute value combinations for each rules table (205). Thebusiness user defines the outputs (settings) that are maintained by thesystem (206). The business user then assigns one or more settings toeach rules table. In one embodiment of the invention, each setting canonly be assigned to one rules table. In each rules table, the businessuser can then specify the value of a setting for each tuple of interest(208), after which the process is completed (209). An embodiment of theinvention performs the task of maintaining data combinations for theuser and can be used across any business model and is not limited to theexamples illustrated herein.

Computer Implementation

FIG. 5 is a block schematic diagram that depicts a machine in theexemplary form of a computer system 1600 within which a set ofinstructions for causing the machine to perform any of the hereindisclosed methodologies may be executed.

In alternative embodiments, the machine may comprise or include anetwork router, a network switch, a network bridge, personal digitalassistant, a cellular telephone, a Web appliance or any machine capableof executing or transmitting a sequence of instructions that specifyactions to be taken.

The computer system 1600 includes a processor 1602, a main memory 1604and a static memory 1606, which communicate with each other via a bus1608.

The computer system 1600 may further include a display unit 1610, forexample, a liquid crystal display (LCD) or a cathode ray tube (CRT). Thecomputer system 1600 also includes an alphanumeric input device 1612,for example, a keyboard; a cursor control device 1614, for example, amouse; a disk drive unit 1616, a signal generation device 1618, forexample, a speaker, and a network interface device 1628.

The disk drive unit 1616 includes a machine-readable medium 1624 onwhich is stored a set of executable instructions, i.e. software, 1626embodying any one, or all, of the methodologies described herein below.The software 1626 is also shown to reside, completely or at leastpartially, within the main memory 1604 and/or within the processor 1602.The software 1626 may further be transmitted or received over a network1630 by means of a network interface device 1628.

In contrast to the system 1600 discussed above, a different embodimentuses logic circuitry instead of computer-executed instructions toimplement processing entities. Depending upon the particularrequirements of the application in the areas of speed, expense, toolingcosts, and the like, this logic may be implemented by constructing anapplication-specific integrated circuit (ASIC) having thousands of tinyintegrated transistors. Such an ASIC may be implemented with CMOS(complementary metal oxide semiconductor), TTL (transistor-transistorlogic), VLSI (very large systems integration), or another suitableconstruction. Other alternatives include a digital signal processingchip (DSP), discrete circuitry (such as resistors, capacitors, diodes,inductors, and transistors), field programmable gate array (FPGA),programmable logic array (PLA), programmable logic device (PLD), and thelike.

It is to be understood that embodiments may be used as or to supportsoftware programs or software modules executed upon some form ofprocessing core (such as the CPU of a computer) or otherwise implementedor realized upon or within a machine or computer readable medium. Amachine-readable medium includes any mechanism for storing ortransmitting information in a form readable by a machine, e.g. acomputer. For example, a machine readable medium includes read-onlymemory (ROM); random access memory (RAM); magnetic disk storage media;optical storage media; flash memory devices; electrical, optical,acoustical or other form of propagated signals, for example, carrierwaves, infrared signals, digital signals, etc.; or any other type ofmedia suitable for storing or transmitting information.

Although the invention is described herein with reference to thepreferred embodiment, one skilled in the art will readily appreciatethat other applications may be substituted for those set forth hereinwithout departing from the spirit and scope of the invention.Accordingly, the invention should only be limited by the Claims includedbelow.

1. A computer implemented method for creating, updating, and deleting business rules, comprising: a processor accepting a set of defined attributes which represent a known state of an application session in which rules are evaluated, where each attribute is an enumeration with a set of enumerators; said processor accepting a set of rules tables, each of which contains one or more of the defined attributes; for each rules table, said processor generating a set of tuples, where each tuple represents one or more respective attribute value combinations and where no two tuples represent the same attribute value combination; for each rules table, said processor accepting a set of settings, where the setting is assigned a value for each tuple; a runtime interface with which an application sets each attribute to a value; and said rules manager providing the value of a setting requested by the application by using a rules table associated with the setting and looking up the setting value assigned to the tuple whose combination of enumerators matches the current value of the corresponding attributes.
 2. The method of claim 1, said rules manager providing an administrative environment for creating, maintaining, and managing attributes, settings, and rules tables, and a runtime interface with which said rules tables look up and return setting values in real-time.
 3. The method of claim 1, wherein said processor automatically generates for each rules table one or more tuples, each of which represents a unique combination of enumerators for the attributes present in the rules table, and which collectively represent all possible combinations of said enumerators for said attributes in the rules table.
 4. The method of claim 3, further comprising: removing from a rules table a combination of attribute values that are of no interest, wherein a subset of the possible attribute value combinations remain in the rules table.
 5. The method of claim 1, wherein the value of a setting assigned to a tuple is independent from the setting value of any other tuple, such that the setting value of one tuple cannot override a setting value of another tuple.
 6. The method of claim 1, wherein said processor determines a setting value from a rules table by finding a tuple that represents said combination of input values in effect at the time of the request.
 7. The method of claim 3, said processor further providing: a wild card entry for use as an attribute value in a tuple to indicate all possible enumerators for that attribute; and an ordering of attributes in a rules table wherein when a tuple has a wildcard in one attribute, then all following attributes are also set to wild cards
 8. The method of claim 7, said wild card entry further comprising an operation for expanding a tuple with said wild card entry to a set of tuples, each of which contains a unique enumerator value of the expanded attribute
 9. The method of claim 7, said wild card entry further comprising a reverse operation for collapsing a set of tuples that are otherwise identical, except for an enumerator value of a given attribute in each tuple, into a single tuple that has a wild card entry for that attribute.
 10. The method of claim 1, wherein every attribute has a default value, wherein when a business application does not explicitly set a value of an attribute during an application session, said attribute is considered to have a value equal to a default value,
 11. The method of claim 1, wherein every attribute is set to an allowable value at each point during an application session.
 12. The method of claim 1, wherein each setting is associated with only one rules table, wherein the rules table to use for a setting is automatically determined without a business application explicitly specifying the rules table to use.
 13. The method of claim 1, further comprising: said business rules manager configured for responding to a business application, when said business application calls upon said business rules manager, by evaluating settings (outcomes or output variables) for said business application.
 14. The method of claim 1, wherein each possible value combination for an attribute is represented by one and only one tuple.
 15. The method of claim 1, further comprising: said rules manager recalculating said set of tuples for a rules table in response to any of addition, deletion, and modification of an attribute enumerator to ensure that all possible valid attribute value combinations are present, and that no invalid attribute value combinations are present, wherein invalid attribute value combinations are those that contain at least one attribute value that is not in its corresponding attribute's set of enumerators.
 16. The method of claim 1, further comprising: said rules manager automatically updating all tables that contain an attribute when an enumerator is added to said attribute to ensure that all possible attribute value combinations are represented.
 17. The method of claim 1, further comprising: said rules manager automatically updating all tables that contain an attribute when an enumerator is removed from that attribute by deleting all tuples that include the removed enumerator.
 18. The method of claim 1, further comprising: said rules manager sorting or filtering rows in a rules table to present a combination of attribute values of interest to a business user.
 19. The method of claim 1, wherein a business application has knowledge of said attributes and settings, but not of said tuples or rows within said rules table; wherein updating and restructuring of said rules table by adding or removing attributes and by moving settings from one rules table to another is performed independently of, and without impact on, said business application.
 20. The method of claim 1, further comprising: multiple versions of said rules table; wherein multiple rules tables can be in use concurrently.
 21. The method of claim 1, further comprising: said rules manager capturing snapshots of the state of said rules table at a point in time, for later reinstatement. 